Security system

ABSTRACT

Methods, systems, computer-readable media, and apparatuses for expanding the functionality of a security system are disclosed. The security system may be integrated with a vehicle security system. For example, a vehicle security node of a vehicle may transmit a signal that may be received by the security system. The security system may authenticate the vehicle security node and integrate the vehicle security node into its network. Various information may be communicated in both directions between the security system and the vehicle security node. The vehicle security node may communicate with an alarm panel that may include a dock for connecting a portable device.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional ApplicationNo. 61/428,589, filed Dec. 30, 2010 and entitled “Home Security SystemUser Devices,” U.S. Provisional Application No. 61/428,603, filed Dec.30, 2010 and entitled “Home Security System Access And Control,” andU.S. Provisional Application No. 61/428,594, filed Dec. 30, 2010 andentitled “Home Security System Infrastructure,” the entire contents ofwhich are hereby incorporated by reference as non-limiting exampleembodiments.

BACKGROUND

The present disclosure relates generally to security systems.

Electronic security systems are a popular way of securing and monitoringproperty. More and more homes, businesses, and other structures havepremises security systems. Security systems are also found inautomobiles. While security systems have been useful for detectingcertain types of intrusions or attempted thefts, there remains anever-present need to improve their coverage ability and convenience ofuse.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the disclosure. The summary is not anextensive overview of the disclosure. It is neither intended to identifykey or critical elements of the disclosure nor to delineate the scope ofthe disclosure. The following summary merely presents some concepts ofthe disclosure in a simplified form as a prelude to the descriptionbelow.

Some aspects of this disclosure relate to extending a premises securitysystem to communicate with a vehicle. For example, by using one or moreaspects of the disclosure, a security system user, such as a caretaker,business owner, or homeowner, may be able to integrate their vehicle'salarm system and their main premises security system. In onearrangement, the security system may receive a signal transmitted from avehicle security node. The security system may authenticate the vehiclesecurity node and the alarm system of the vehicle may be integrated withthe security system. Thus, information may be exchanged in bothdirections between the security system and the vehicle security node.

In another aspect of this disclosure, the premises security system mayinclude an alarm panel that includes a dock having a keypad and anadapter. The adapter allows a portable device to connect to the dock.When connected to the dock, the portable device may obscure the keypadof the dock, and may launch a security system application and display akeypad on its own or a remote screen, allowing the portable device toserve as the home security interface.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 illustrates an example communication network according to one ormore aspects described herein.

FIG. 2 illustrates an example computing device according to one or moreaspects described herein.

FIG. 3 illustrates a diagram of an example operating environmentaccording to one or more aspects described herein.

FIG. 4 illustrates an example security system according to one or moreaspects described herein.

FIG. 5 illustrates an example process of registering a security nodeaccording to one or more aspects described herein.

FIG. 6 illustrates an example process according to one or more aspectsdescribed herein.

FIG. 7 illustrates another example process according to one or moreaspects described herein.

FIG. 8 illustrates yet another example process according to one or moreaspects described herein.

FIG. 9 illustrates an example alarm panel according to one or moreaspects described herein.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

FIG. 1 illustrates an example network 100 on which many of the variousfeatures described herein may be implemented. Network 100 may be, forexample, any type of information distribution network, such assatellite, telephone, cellular, wireless, etc. One example may be anoptical fiber network, a coaxial cable network, or a hybrid fiber/coaxdistribution network. Such networks 100 use a series of interconnectedcommunication links 101 (e.g., coaxial cables, optical fibers, wireless,etc.) to connect multiple premises 102 (e.g., businesses, homes,consumer dwellings, etc.) to a local office or headend 103. The localoffice 103 may transmit downstream information signals onto the links101, and each premises 102 may have a receiver used to receive andprocess those signals.

There may be one link 101 originating from the local office 103, and itmay be split a number of times to distribute the signal to variouspremises 102 in the vicinity (which may be many miles) of the localoffice 103. The links 101 may include components not illustrated, suchas splitters, filters, amplifiers, etc. to help convey the signalclearly, but in general each split introduces a bit of signaldegradation. Portions of the links 101 may also be implemented withfiber-optic cable, while other portions may be implemented with coaxialcable, other lines, or wireless communication paths.

The local office 103 may include an interface, such as a terminationsystem (TS) 104. In one example, the interface 104 may be a cable modemtermination system (CMTS), which may be a computing device configured tomanage communications between devices on the network of links 101 andbackend devices such as servers 105-107 (to be discussed further below).The interface 104 may be as specified in a standard, such as the DataOver Cable Service Interface Specification (DOCSIS) standard, publishedby Cable Television Laboratories, Inc. (a.k.a. CableLabs), or it may bea similar or modified device instead. The interface 104 may beconfigured to place data on one or more downstream frequencies to bereceived by modems at the various premises 102, and to receive upstreamcommunications from those modems on one or more upstream frequencies.

The local office 103 may also include one or more network interfaces108, which can permit the local office 103 to communicate with variousother external networks 109. These networks 109 may include, forexample, networks of Internet devices, telephone networks, cellulartelephone networks, fiber optic networks, local wireless networks (e.g.,WiMAX), satellite networks, and any other desired network, and thenetwork interface 108 may include the corresponding circuitry needed tocommunicate on the external networks 109, and to other devices on thenetwork such as a cellular telephone network and its corresponding cellphones.

As noted above, the local office 103 may include a variety of computingdevices, such as servers 105-107 that may be configured to performvarious functions. For example, the local office 103 may include a pushnotification server 105. The push notification server 105 may generatepush notifications to deliver data and/or commands to the variouspremises 102 in the network (or more specifically, to the devices in thepremises 102 that are configured to detect such notifications). Thelocal office 103 may also include a content server 106. The contentserver 106 may be one or more computing devices that are configured toprovide content to users at their premises. This content may be, forexample, video on demand movies, television programs, songs, textlistings, etc. The content server 106 may include software to validateuser identities and entitlements, to locate and retrieve requestedcontent, to encrypt the content, and to initiate delivery (e.g.,streaming) of the content to the requesting user and/or device.

The local office 103 may also include one or more application servers107. An application server 107 may be a computing device configured tooffer any desired service, and may run various languages and operatingsystems (e.g., servlets and JSP pages running on Tomcat/MySQL, OSX, BSD,Ubuntu, Redhat, HTML5, JavaScript, AJAX and COMET). For example, anapplication server may be responsible for collecting television programlistings information and generating a data download for electronicprogram guide listings. Another application server may be responsiblefor monitoring user viewing habits and collecting that information foruse in selecting advertisements. Still, another application server maybe responsible for receiving and transmitting communications related toa security system in accordance with the present disclosure. Althoughshown separately, one of ordinary skill in the art will appreciate thatthe push server 105, content server 106, and application server 107 maybe combined. Further, here the push server 105, content server 106, andapplication server 107 are shown generally, and it will be understoodthat they may each contain memory storing computer executableinstructions to cause a processor to perform steps described hereinand/or memory for storing data collected, such as security systemsettings, vehicle security node profiles, user and/or vehicle schedules,and alarm event logs, as a result of performing steps described herein.

An example premises 102 a, such as a home, may include an interface 110.For example, the interface 110 may include a modem 111, which mayinclude transmitters and receivers used to communicate on the links 101and with the local office 103. The modem 111 may be, for example, acoaxial cable modem (for coaxial cable lines 101), a fiber interfacenode (for fiber optic lines 101), or any other desired modem device.Also, although only one modem is shown in FIG. 1, a plurality of modemsoperating in parallel may be implemented within the interface 110.Further, the interface 110 may include a gateway interface device 112.The modem 111 may be connected to, or be a part of, the gatewayinterface device 112. The gateway interface device 112 may be acomputing device that communicates with the modem(s) 111 to allow one ormore other devices in the premises 102 a, to communicate with the localoffice 103 and other devices beyond the local office 103. The gateway112 may be a set-top box (STB), digital video recorder (DVR), computerserver and/or router, or any other desired computing device. The gateway112 may also include (not shown) local network interfaces to providecommunication signals to requesting entities/devices in the premises 102a, such as televisions 113, additional STBs 114, personal computers 115,laptop computers 116, wireless devices 117 (e.g., wireless routers,wireless laptops, notebooks, tablets and netbooks, cordless phones(e.g., Digital Enhanced Cordless Telephone—DECT phones), mobile phones,mobile televisions, personal digital assistants (PDA), etc.), landlinephones 118, an alarm panel 119, and any other desired devices. Examplesof the local network interfaces include Multimedia Over Coax Alliance(MoCA) interfaces, Ethernet interfaces, universal serial bus (USB)interfaces, wireless interfaces (e.g., IEEE 802.11, IEEE 802.16), analogtwisted pair interfaces, Bluetooth interfaces, and others.

FIG. 2 illustrates general hardware elements that can be used toimplement any of the various computing devices discussed herein. Thecomputing device 200 may include one or more processors 201, which mayexecute instructions of a computer program to perform any of thefeatures described herein. The instructions may be stored in any type ofcomputer-readable medium or memory, to configure the operation of theprocessor 201. For example, instructions may be stored in a read-onlymemory (ROM) 202, random access memory (RAM) 203, removable media 204,such as a Universal Serial Bus (USB) drive, compact disk (CD) or digitalversatile disk (DVD), floppy disk drive, or any other desired storagemedium. Instructions may also be stored in an attached (or internal)hard drive 205. The computing device 200 may include one or more outputdevices, such as a display 206 (e.g., an external television), and mayinclude one or more output device controllers 207, such as a videoprocessor. There may also be one or more user input devices 208, such asa remote control, keyboard, mouse, touch screen, microphone, etc. Thecomputing device 200 may also include one or more network interfaces,such as a network input/output (I/O) circuit 209 (e.g., a network card)to communicate with an external network 210. The network input/outputcircuit 209 may be a wired interface, wireless interface, or acombination of the two. In some embodiments, the network input/outputcircuit 209 may include a modem (e.g., a cable modem), and the externalnetwork 210 may include the communication links 101 discussed above, theexternal network 109 discussed above, an in-home network, a provider'swireless, coaxial, fiber, or hybrid fiber/coaxial distribution system(e.g., a DOCSIS network), or any other desired network.

The FIG. 2 example is a hardware configuration. Modifications may bemade to add, remove, combine, divide, etc. components of the computingdevice 200 as desired. Additionally, the components illustrated may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 201, ROM storage 202, display 206, etc.) maybe used to implement any of the other computing devices and componentsdescribed herein. For example, the various components herein may beimplemented using computing devices having components such as aprocessor executing computer-executable instructions stored on acomputer-readable medium, as illustrated in FIG. 2. Some or all of theentities described herein may be software based, and may co-exist in acommon physical platform (e.g., a requesting entity can be a separatesoftware process and program from a dependent entity, both of which maybe executed as software on a common computing device). Additionally, forthe security system described herein, the computing device 200 mayinclude a security system manager 201 a, which can perform the varioussecurity functions described herein as a replacement for, or augment to,any other processor 201 that the computing device 200 may include. Thatis, the security system manager 201 a may include a separate set ofcomputer-executable instructions stored on a computer-readable mediumthat, when executed by a processor (e.g., processor 201), cause theprocessor (or the computing device 200 as a whole) to perform thevarious security functions described herein. The security system manager201 a may also include internal secure memory (not shown), which canstore the various security settings, vehicle security node settings,profiles, alarm event logs, and computer-executable instructions forperforming security system processes, such as registering sensors,registering vehicle security nodes, communicating with vehicle securitynodes, detecting alarm events, reacting to alarm events, andcommunicating alarm events over external networks described herein. Theinternal memory can be any desired type of memory, and can have enhancedsecurity features to help restrict access (e.g., can only be accessed bythe security system manager 201 a). Where the security system manager201 a includes a separate set of computer-executable instructions, theseinstructions may be secured such that only authorized users (e.g., thoseproviding a password) may be allowed to modify, augment, or delete them.

In some embodiments, the security system manager 201 a may beimplemented as an application specific integrated circuit (ASIC). Thatis, the security system manager 201 a may be a chip designedspecifically for performing the various security functions describedherein. Further, the ASIC may be implemented within or in communicationwith various computing devices provided herein.

One or more aspects of the disclosure may be embodied in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. As will be appreciated by one of skill in the art, thefunctionality of the program modules may be combined or distributed asdesired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more aspects of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

FIG. 3 is a diagram showing an example operating environment in whichvarious features described herein may be performed and implemented. Theenvironment may include a premises 300 (which may correspond to thepremises 102 of FIG. 1), such as a user residence, business,recreational facility, etc. (referred to herein as a user residence orpremises in a non-limiting manner), a vehicle 301, and a local office302 (which may correspond to the local office 103 of FIG. 1). One ormore properties located on the premises 300, such as a television 303,may be secured according to one or more aspects described herein. Thepremises 300 may include one or more doors 304 and a plurality ofwindows 305. The doors 304 may be secured by an associated door securitysensor 306 (e.g., a proximity sensor, contact switch, motion detector,etc.). In addition, each of the plurality of windows 305 may be securedby associated window security sensors 307, which may be similar to thedoor security sensor 306. The security sensors 306 and 307 may becommunicatively coupled to an alarm panel 308, which may allow thesecurity sensors 306 and 307 to be armed, disarmed, and monitored. Forinstance, a user may operate alarm panel 308 to arm security sensors306, such that if a door 304 is opened while the associated securitysensor 306 is armed, an alarm will be triggered. Herein, triggering analarm may result in various actions, for example, playing an alarmsound, presenting an alarm message, turning on/off lights, turning oncameras, etc. In one arrangement, the alarm panel 308 may be implementedin and/or as part of gateway 309. Thus, in one example, gateway 309 maybe communicatively coupled to security sensors 306 and 307, which mayallow gateway 309 to arm, disarm, and/or monitor the security sensors306 and 307. While the description above focuses on door securitysensors 306 and window security sensors 307, many other security sensorsand devices may be communicatively coupled to the alarm panel 308 and/orgateway 309. For example, the alarm panel 308 may be communicativelycoupled to one or more cameras 310, which may record video to monitorthe premises 300 and surrounding area.

Further, as shown in FIG. 3, the alarm panel 308 and/or gateway 309 maybe communicatively coupled to a mobile security node (not shown) withinthe vehicle 301. In the examples throughout this disclosure, whenattached to the vehicle 301, the mobile security node may be referred toas a vehicle security node. The vehicle 301 may be any type of vehicle,including an automobile (e.g., car, truck, bus, etc.), watercraft,recreational vehicle (R/V), motorcycle, bicycle, aircraft, etc. In someembodiments, the vehicle 301 may have an existing alarm system (e.g., acar alarm system). The vehicle 301 may have been manufactured with thealarm system or it may have been installed thereafter. Such vehiclealarm systems may be capable of detecting impact, glass breaking,door/window opening, vibrations, and/or nearby movement. In addition,the vehicle 301 may be outfitted with specially designed vehicle sensors311 for use with a security system in accordance with the presentdisclosure. In particular, the vehicle sensors 311 may be designed orlater adapted to communicate with the alarm panel 308 and/or gateway 309via the vehicle security node. In one or more arrangements, the vehiclesensors 311 may be integrated with the vehicle security node. That is,the vehicle security node may act as a vehicle sensor 311. Although FIG.3 shows only one vehicle 301, a plurality of vehicles 301 maycommunicate simultaneously with the alarm panel 308 and/or gateway 309.

The mobile security node or vehicle security node can be implemented asa computing device, and can be a dedicated security device akin to atraditional car alarm and computing systems. Alternatively, the mobilesecurity node can be implemented as any other portable computing device,such as a smartphone, tablet, house key, etc. As mentioned above, themobile security node may be referred to as a vehicle security node forclarity. However, use of the term “vehicle security node” should beinterpreted in a non-limiting manner, and where reference is made to avehicle, vehicle security node, and vehicle sensors, the functions andfeatures of these elements may be similarly implemented with a mobiledevice (e.g., a smartphone, tablet, house key, etc.), a mobile securitynode, and sensors designed/adapted for a mobile device. Therefore, wherea mobile security node is implemented on, for example, a smartphone, analarm system of the smartphone may be integrated with the securitysystem of the premises 300 when the mobile security node is in range ofthe security system.

From the example diagram of FIG. 3, various features may be realized.For example, the security sensors 306 and 307, vehicle sensors 311,mobile security nodes, cameras 310, alarm panel 308, and gateway 309 maybe communicatively coupled to a user interface device, such as thetelevision 303 (or another type of display). Through the user interfacedevice (e.g., the television 303) an authorized user may configure anyof the devices within the security system. Another example feature mayinclude transmitting (e.g., streaming) data (e.g., pictures, video,audio, etc.) from one or more cameras 310 to any of the other devices inthe diagram of FIG. 3.

FIG. 3 also shows that the gateway 309 may communicate with an externalnetwork, such as the local office 302. Thus, the gateway 309 maytransfer alert signals indicating detected alarm events upstream to thelocal office 302. This may be particularly desired to counter “smash andgrab” scenarios in which an intruder smashes devices of the securitysystem (e.g., alarm panel 308, camera 310, security sensors 306 and 307,etc.) in hopes of disabling the alarm event or preventing recording ofthe alarm event. In a smash and grab scenario, the gateway 309 maytransfer alert signals upstream to the local office 302 so that theauthorities can be alerted and/or data regarding the alarm event can becaptured before the security system is disabled.

Referring to FIG. 3, when an alarm event is detected, the local office302 may record the alarm event (e.g., store information identifying thesensor(s) that were tripped, their location, recording video and/oraudio showing the event that occurred, etc.), determine an appropriatereaction, and/or transmit a signal to an external network, such as thepublic switched telephone network (PSTN) 312 or a wide area network(WAN) 313. In one embodiment, the gateway 309 may communicate directlywith networks 312, 313, and 316

Via the PSTN 312, the local office 302 may transfer an alert signal to acell tower 314 and ultimately to a designated cellular device 315 (e.g.,smartphone, tablet, etc.). Also, through the PSTN 312, the local office302 may connect to a public safety answering point (PSAP) 316. Thus, thelocal office 302 may alert authorities of the alarm, so that theauthorities may be dispatched to the premises 300 or vehicle 301.

Additionally, or alternatively, the local office 302 may transfer analert signal via the WAN 313 (e.g., the Internet) to a monitoring entity317 and/or a web portal server 318. The monitoring entity 317 may be thesame entity as the local office 302 or a third party entity. Regardless,the monitoring entity 317 may be responsible for monitoring the premises300. This may include responding to alert signals received when thesecurity system detects an alarm event. For example, the monitoringentity 317 may immediately contact appropriate authorities to dispatchthem to the premises 300. Or, when an alert signal is transferred to themonitoring entity 317, this may prompt a representative or automatedsystem of the monitoring entity 317 to call the premises or anotherdesignated number to confirm the truthfulness of the alarm event.

Meanwhile, the web portal server 318 may be a computing device capableof providing a web portal through which users may view, on any connecteddisplay device, information regarding the security of the premises 300and vehicle 301. Users may log-on to the web portal provided by the webportal server 318 and view an alarm event and/or information related toan alarm event, such as what sensor was triggered and when it wastriggered. Also through the web portal, a user may be able to view videoof the premises 300 captured by the camera 310 or may be able to checkthe status of the security system to see if it is armed. Where the webportal server 318 is coupled to a WAN 313, such as the Internet, the webportal for the premises 300 may be accessed using any device that canconnect to the WAN 313, such as a smartphone, tablet, laptop, etc. Theweb portal may also be used to customize settings, such as schedules, toindicate when and how the security system should operate. For instance,using the web portal a user may be able to indicate certain times duringwhich the security system should automatically arm itself if the vehicle301 is away from the premises 300.

In some embodiments, the web portal may permit a user to view multiplepremises 300. That is, a single interface may allow a user to viewstatus information, video, security settings, etc. for a plurality ofpremises 300. In some cases, such information may be viewedsimultaneously on the web portal. Having a single interface may bedesirable to users who have multiple security systems at various remotelocations, such as users who own multiple homes or businesses.

FIG. 4 illustrates an example security system 400 that may be used insecuring a premises 300 and/or one or more properties (e.g., vehicle301) according to one or more aspects described herein. Security system400 may include one or more security sensor nodes 410 (which maycorrespond to or be used with security sensors 306 and 307, cameras 310,and/or vehicle sensors 311 of FIG. 3), an alarm panel 420 (which maycorrespond to alarm panel 308 of FIG. 3), and a gateway 430 (which maycorrespond to gateway 309 of FIG. 3) communicatively coupled to oneanother via a local area network (LAN) 401, which may include variouslinks and repeaters (not shown) and which may be communicatively coupledto an external network 402 (e.g., a WAN). Further, one or more vehiclesecurity nodes 440 may be placed in a vehicle 301 to be integrated withthe security system 400. These example components are described ingreater detail below.

According to one or more aspects, one or more security sensor nodes 410may be attached to various objects, or coupled to sensors attached tovarious objects, that are to be secured, such as windows, doors,furniture (e.g., a chair, a table, an armoire), electronic equipment(e.g., a television, a stereo, a video game console, a computer, atelephone), a fixture (e.g., a safe, a chandelier, a painting, a grill,etc.), etc.

Various security sensor nodes 410 may include various components. Forexample, a complex security sensor node 410 may include one or moreprocessors 411 configured to execute software instructions stored on amemory 412 (e.g., any computer-readable medium, such as flash memory ora hard drive) to perform various functions described herein.

The security sensor node 410 may include one or more user interfaces413. The user interfaces 413 may be, for example, any desired type ofdevice to allow interaction with a user, such as buttons, lights, LEDdisplays, audio speakers, etc. Additionally, the security sensor node410 may include a local area network (LAN) interface 414. The LANinterface 414 may implement any desired type of communication medium forcommunicating signals between all components in the premises. Forexample, the LAN interface 414 may be a wireless IEEE 802.11 interface,allowing the security sensor node 410 to wirelessly communicate with thealarm panel 308, gateway 430, one or more vehicle security nodes 440,and/or other devices. Other wireless interfaces could be used as well,such as 802.15.4, ZigBee, Z-Wave, Bluetooth, etc. The LAN interface 414can also use a wired medium, such as a MoCA (Multimedia Over CoaxAlliance) interface connected to the in-home coaxial cable network, orto an Ethernet network.

The security sensor node 410 may also include one or more accelerometers415, which may be configured to detect acceleration and/or movementalong one or more axes. Additionally, or alternatively, the securitysensor node 410 may include one or more magnetometers 416, which may beconfigured to detect magnetic fields for directional orientation (e.g.,north, south) and/or proximity between two items (e.g., an inductioncoil on a window frame whose magnetic field is disturbed by theproximity of a second component on the window itself). Of course, someof the detection described herein may be performed by the processor 411,based on readings taken from the accelerometer 415 and/or magnetometer416. Other types of sensing devices may be included within or coupled tothe security sensor node 410 as well, such as contact switches, infraredmotion detectors, microphone sound detectors, cameras, thermal sensors,etc.

The security sensor node 410 may also include other components (notshown), such as a battery or other power supply, an indicator light, andan antenna, as well as additional accelerometers, magnetometers,transceivers, processors, memory, and input/output interfaces.

The various motion, position, location, movement, etc. detected by thesecurity sensor node 410 may be reported via the LAN interface 414 tothe alarm panel 420. The alarm panel 420 may operate within securitysystem 400 to monitor one or more security sensor nodes 410 included insecurity system 400, and may provide additional functionalities, such asallowing a user to arm security system 400 and/or security sensor nodes410. For instance, alarm panel 420 may be attached to a wall near anentrance to a secured area, and a user may interact with alarm panel 420to arm security system 400 and/or security sensor nodes 410. Inaddition, alarm panel 420 may include a plurality of components, asfurther described below, that may enable alarm panel 420 to communicatewith other devices included in security system 400 and thereby providearming, monitoring, and other functionalities.

To provide such functionalities, the alarm panel 420 may also include aprocessor 421, operating to execute software instructions stored in acomputer-readable memory 422 (e.g., flash, hard drive, etc.). The alarmpanel 420 may include various user interface elements, such as a display423 a and a keypad 423 b for inputting data, such as passcodes, andoutputting data, such as alert messages. Also, the alarm panel mayinclude a LAN interface 424, similar to the LAN interface 414 of thesecurity sensor node 410, in order to communicate with the securitysensor nodes 410, gateway 430, and vehicle security node 440. Moreover,within a single embodiment, the alarm panel 420 may include varioustypes of LAN interfaces 424. For example, the alarm panel 420 mayinclude a wired LAN interface (e.g., a USB interface) for communicatingwith one or more security sensor nodes 410 and a wireless LAN interface(e.g., Zigbee) for communicating with a vehicle security node 440.

Furthermore, in some embodiments, the alarm panel 420 may include a dock900 as shown in FIG. 9. The dock 900 may be configured to receive aportable device 901 (e.g., a tablet, smartphone, etc.). The dock 900 mayinclude a keypad 902 and an adapter 903. The keypad 902 may be hardwired so that communications can be more secure and/or reliable. Usingthe keypad 902, a user may enter a passcode to arm and/or disarm thesecurity system 400. The keypad 902 may also be used to configure thesecurity sensor nodes 410 and vehicle security nodes 440. Meanwhile, theadapter 903 may be any hardware and/or software connection (proprietaryor non-proprietary) that allows the portable device 901 to interfacewith the dock 900. Examples of possible connections include Ethernetconnections, USB connections, portable digital media interface (PDMI)connectors, FireWire connectors, etc. Although not shown, the dock 900may also include a power supply port and a battery to provide back-uppower if needed.

As shown in FIG. 9, the keypad 902 may be positioned on the dock 900such that it would be obscured by the portable device 901 when theportable device is docked (e.g., connected to the dock via adapter 903).When docked, the portable device may become the sole interface between auser and the security system 400. Therefore, the user may use a keypad904 of the portable device 901, instead of the keypad 902 of the dock900. In some embodiments, the keypad 904 of the portable device may beimplemented by displaying a keypad on a touch screen of the portabledevice 901. Further, in one aspect of the present disclosure, the keypad904 of the portable device 901 is automatically displayed when theportable device is docked to the dock 900. More specifically, a securitysystem application installed on the portable device 901 may beautomatically launched (if not already launched) when the portabledevice 901 is connected to the dock 900 and may processcomputer-executable instructions (e.g., a script) to display the keypad904.

The security system application may further provide buttons 905 to armor disarm the security system or to set the security system into anyother mode (e.g., a panic mode, a pre-arm mode, a configuration mode,etc.). In some embodiments, the security application may only allow auser to arm or disarm the security system 400 while the portable device901 is docked. In other embodiments, the portable device 901 may be ableto arm or disarm the security system 400 even when it is not docked.

Additionally, the security system application may allow a user of theportable device 901 to view various information regarding the securitysystem 400. For example, the security system application may give a useraccess to the status (armed, disarmed, etc.) of the security system 400,information on alarm events detected, video of an alarm event, etc.Further, the security system application may be registered with morethan one security system 400 so that a user may view informationregarding security systems 400 at different locations via a singleinterface.

The dock 900 may also be configured to receive different portabledevices 901. Therefore, when one user removes his/her portable device901 from the dock 900, another user may dock his/her portable device 901at the dock 900. The dock 900 may be able to interface with any portabledevice 901 having an authorized security system application. In someembodiments, the portable device 901 may be authorized so that apasscode for the security system does not need to be entered each timethe portable device 901 is docked. In other embodiments, the securitysystem application may prompt the user for a passcode each time it isdocked. Also, in some embodiments, the dock 900 may be configured totransmit information to and from the portable device 901 only when it isdocked, whereas in other embodiments, the dock 900 may transmitinformation to and from the portable device 901 whether or not it isdocked.

Another feature of the dock 900 may be the ability to charge theportable device 901 while it is docked. This may incentivize users touse their portable devices 901 as interfaces to the security system 400.Such a feature also may allow the portable device 901 to remain dockedfor an extended period of time.

In light of the above, it should be understood that the dock 900 andportable device 901 may have many features that enable them to functionas the alarm panel 420.

Turning back to FIG. 4, in one or more arrangements, the alarm panel 420may also be implemented as hardware and/or software components inanother device, such as gateway 430, which is further described below.Or, some or all of the alarm panel functionality can be duplicated inthe gateway device 430, and the gateway may include similar componentsas those found in the alarm panel 420. For example, gateway 430 mayinclude a processor 431, configured to execute instructions stored on acomputer-readable memory 432. It may also include one or more userinterfaces 433 (e.g., buttons, keypads, infrared remote control, etc.),and a LAN interface 434 to allow communications with the security sensornodes 410, alarm panel 420, vehicle security node 440, and/or with otherdevices on the premises 300.

The gateway 430 may also include other communication devices as well.For example, it may include a device for communicating with an externalnetwork, such as a modem 435. Thus, the gateway 430 may be connected to,and communicate with, the local office 103 or an external network 109.It may also include video processing circuitry 436, which can decodeand/or decrypt incoming video signals, and generate an output videosignal that can be supplied to a display device (e.g., a television303). Accordingly, the gateway 430 may generate one or more userinterface screens, for display on the television 303 or a personalcomputer, that allow a user to arm and disarm security system 400,configure attributes of a security sensor node 410 or vehicle securitynode 440, manage profiles, transmit test alerts, and monitor one or moresecurity sensor nodes 410 and vehicle security nodes 440 included withinthe security system 400. In some embodiments, the gateway 430 may alsoinclude functionality of a traditional television set-top box (STB)and/or a digital video recorder (DVR).

The security system 400, including one or more security sensor nodes410, alarm panel 420, and gateway 430, may be extended to include one ormore vehicle security nodes 440. The vehicle security node 440 mayinclude a processor 441 and memory 442 for storing computer-executableinstructions that when executed by the processor allow the vehiclesecurity node to perform the functions described herein. Moreover, thevehicle security node 440 may include one or more user interfaces,having buttons, lights, a microphone, a display, a keypad, etc., throughwhich a user can configure, evaluate, and/or control the vehiclesecurity node 440. Furthermore, the vehicle security node 440 mayinclude a LAN interface 444. The LAN interface 444 may implement anydesired type of communication medium for communicating signals betweenthe vehicle security node and the other components in the premises. Forexample, the LAN interface 444 may be a wireless IEEE 802.11 interface,allowing the vehicle security node 440 to wirelessly communicate withthe security sensor nodes 410, alarm panel 420, and/or gateway 430.Other wireless interfaces may be used too, such as 802.15.4, ZigBee,Z-Wave, Bluetooth, Satellite, Cellular, etc. The LAN interface 444 canalso use a wired medium, such as a MoCA (Multimedia Over Coax Alliance)interface connected to the in-home coaxial cable network, or to anEthernet network. For example, when the vehicle is parked in a garage,the vehicle security node 440 may easily be wired to the other devicesof the security system 400.

Additionally, the vehicle security node 440 may have a sensor interface445 for communicating with one or more vehicle sensors 311 located onthe same vehicle 301. The vehicle sensors 311 may include accelerometers415, magnetometers 416, etc. and may be used to measure or detecttemperature, pressure, impact, motion, glass breakage, etc. The vehiclesensors 311 may communicate with the vehicle security node 440 overwired or wireless connections. Also, the communications between thevehicle sensors 311 and the vehicle security node 440 may use anyprotocol, such as Ethernet, USB, IEEE 802.11, etc. In one or morearrangements, the vehicle security node 440 may include one or morevehicle sensors 311 so that the vehicle security node may itself detectan alarm event. In other words, the vehicle security node 440 andvehicle sensors may be one in the same. In such arrangements, the sensorinterface 445 may serve to input data (e.g., an alert signal) indicatingan alarm event.

Further, the vehicle security node 440 may include a vehicle alarminterface 446. The vehicle alarm interface 446 may be any desired wiredor wireless connection, and may connect the vehicle security node 440 tothe vehicle's pre-existing alarm system. Pre-existing vehicle alarmsystems may include contact sensors, shock sensors, glass breakagesensors, magnetic contact sensors, motion sensors, perimeter (radar)sensors, etc. in order to detect impact, vibrations, heat, glassbreakage, etc. By connecting to the pre-existing alarm system, thevehicle security node 440 may detect whenever the pre-existing alarmsystem is triggered. As a result, the vehicle security node 440 maynotify the gateway 430, alarm panel 420, and/or other security sensornodes 410 when the pre-existing alarm system is triggered.

Moreover, the vehicle security node 440 may include a diagnosticinterface 447, which is configured to connect to a vehicle's On-BoardDiagnostic (OBD) system via the OBD-II connector. The OBD-II connectoris a well-known connector in the automotive industry and is used tooutput diagnostic data from a vehicle 301. The diagnostic interface 447may scan the vehicle's data bus and retrieve the OBD-II codes, which mayindicate various information about the vehicle, such as fuel systemstatus, engine coolant temperature, fuel pressure, engine oiltemperature, etc. The diagnostic interface 447 may directly connect tothe OBD-II connector or may wirelessly connect to the OBD-II connector.Further, the diagnostic interface 447 may be configured to relay theinformation obtained from the vehicle's bus to the LAN interface 444 sothat the information may be transferred to the gateway 430, alarm panel420, security sensor nodes 410, or other devices upstream. Accordingly,information regarding the status of the vehicle 301 may be ascertainedfrom the display 423 a on the alarm panel 420 and/or from a deviceconnected to the video processing circuitry 436 of the gateway 430.

It should be understood that the configurations of the differentcomponents are shown by way of example and are not intended to belimiting. For example, the vehicle security node 440 may not have asensor interface 445 to communicate with additional sensors, andinstead, may rely solely on the sensors of the pre-existing alarmsystem.

FIG. 5 illustrates an example process of registering a vehicle securitynode 440 with the security system 400. Once the new vehicle securitynode 440 is installed on the vehicle 301 and powered on, the securitysystem 400 may detect its presence in step 501. Such detection of thepresence of the new vehicle security node 440 may occur automatically.For instance, the alarm panel 420 and/or gateway 430 may use a wirelesslocal area network to search for the newly-introduced vehicle securitynode 440. Alternatively, the newly-introduced vehicle security node 440may be placed in a “pairing” mode when it is installed. While in thepairing mode, the vehicle security node 440 may transmit a distributedsignal (e.g., a broadcast radio signal) indicating that the vehiclesecurity node 440 is new and/or online. The gateway 430 and/or alarmpanel 420 may detect this broadcast signal, thereby learning of the newvehicle security node 440. Alternatively, the gateway and/or alarm panelmay simply be told by the user that a new vehicle sensor node 440 hasbeen installed (e.g., by a menu option, or pressing a predefined “addvehicle security node” button, entering a code identifying the vehiclesecurity node 440, etc.).

Step 501 may be performed until the vehicle security node 440 isdetected. When the vehicle security node 440 is detected, the process ofregistering the vehicle security node 440 may proceed to step 502. Instep 502, it is determined whether or not the vehicle security node 440has a predefined security profile. Herein, the security profile defineswhat a vehicle security node 440 will sense and how the security system400 will interact with the vehicle security node 440 including how itwill react to information received from the vehicle security node 440.In some embodiments, a vehicle security node 440 may include apredefined profile. A manufacturer or other pre-installation distributormay offer a data file (stored in the vehicle security node 440 oravailable for downloading) containing a set of instructions forcommunicating with the security system 400. The instructions may controlthe vehicle security node 440 to, for example, transfer certaindiagnostic information obtained through the OBD-II connectors ortransfer notifications that the pre-existing vehicle alarm system hasbeen triggered to the security system 400. The instructions may alsocontrol how the gateway 430 or alarm panel 420 respond to informationreceived from the vehicle security node 440. For example, the predefinedprofile may include instructions that cause the gateway 430 or alarmpanel 420 to arm the security system 400 when the vehicle security node440 no longer transmits a signal thereby indicating that the vehicle hasleft the proximity of the security system 400. The predefined profilesmay be a software download made available to purchasers of the vehiclesecurity node 440, or the software could be distributed oncomputer-readable media (e.g., a CD, built-in or external flash drive,etc.) with the vehicle security node 440.

Alternatively, the gateway 430 and/or alarm panel 420 may automaticallystore a database containing many different predefined security profiles(e.g., the gateway's security system software may include defaultprofiles for vehicle security nodes 440 that are customized for peoplewho live alone, people who have kids, etc.). Alternatively, the gateway430 may download the predefined profiles from the local office 302 orother entity coupled to the WAN 313. In any case, the gateway 430 maydisplay a list of available profiles that fit the behavior of the user.For example, if the user lives alone, the security system 400 may bearmed whenever the vehicle security node 440 loses communication withthe security system 400, whereas if the user has family members orroommates that have vehicle's 301 with vehicle security nodes 440 aswell, the security system 400 may not arm itself unless all vehicles 301are away from the premises 300.

The determination of whether a predefined profile exists may be made ina variety of ways. For example, if the new vehicle security node 440automatically broadcasts its presence, it can also indicate in thebroadcast that it has a predefined profile in its own memory 442, orthat one is available for download. Alternatively, it could simplyidentify itself with an identifier (e.g., identifying a class of device,manufacturer, model number, serial number, etc.), and the gateway 430could search its own memory 432 to determine if it already has apredefined profile for the new vehicle security node 440. The gateway430 could also transmit a request out onto the Internet or anothernetwork (or a server associated with the maker of the vehicle securitynode 440 or the vehicle 301 being secured) asking if a predefinedprofile exists, and, if it does, requesting to download it.

If a predefined profile exists, then the process may proceed to step503, and the predefined profile may be loaded for use by the gateway 430and/or alarm panel 420. This loading may be done in any desired manner(e.g., copying from a memory 442 of the vehicle security node 440,copying from a memory provided along with the vehicle security node 440,copying from a pre-existing database in the gateway 430, downloadingfrom an external server to the gateway 430, etc.). Once the profile isloaded, the process of registering may end, and the security system 400may begin communicating with the vehicle security node 440.

If, in step 502, no predefined profile exists, then the process mayproceed to step 504, and the user can begin a training process to trainthe security system 400 in using the new vehicle security node 440. Thiscan be initiated, for example, by the gateway 430 or alarm panel 420displaying (e.g., on the alarm panel display 423 a, the television 303,or a computer) a message requesting that the user start the training forthe new vehicle security node 440.

In step 504, the user may train the security system 400 to recognize anapproximate position of the vehicle 301 on which the vehicle securitynode 440 is installed. Once the vehicle security node 440 is installedon the vehicle 301, it may transmit (e.g., broadcast) a signal via itsLAN interface 444. The security system 400 may be trained to receive thetransmitted signal and determine its signal strength. By positioning thevehicle 301 in a desired location (e.g., in a garage, in a driveway, oron the street in front of a premises 300 having the security system 400)and recording the signal strength of the transmitted signal while thevehicle 301 is in that position, the security system 400 may be taughtthe desired position of the vehicle 301. The user may inform the gateway430 or alarm panel 420 when the vehicle is in the desired position, forexample, by pressing a button on the alarm panel 420. After recordingthe signal strength when the vehicle 301 is in the desired position, thesecurity system 400 may determine when the vehicle 301 is moved from thedesired position by detecting a change in the signal strength. Forexample, the security system may determine that the vehicle has left theproximity of the security system 400 when it no longer detects thetransmitted signal from the vehicle security node 440. In someembodiments, the security system 400 may be taught a permissible rangein which the vehicle 301 may be positioned with respect to the securitysystem 400. For example, it may be acceptable for the vehicle to beparked in any spot on the street in front of a house having the securitysystem 400, but not acceptable if the vehicle 301 is parked on theopposite side of the street. Or, it may be acceptable if the vehicle 301is in the garage, but not in the driveway.

Additionally, multiple points and corresponding tasks may be designated.For example, the user may wish to turn on lights along the driveway whenthe vehicle 301 is at one distance, open a garage door when it's at acloser distance, and disarm the security system 400 and/or turn oninside lights when the vehicle is at an even closer distance. Each ofthese points may be associated with a recorded signal strength of thesignal received from the vehicle security node 440. While the abovedescription explains how step 504 can train the security system 400 toidentify positions of the vehicle 301, step 504 may also be performed tosimply train the security system 400 to recognize the vehicle securitynode 440. That is, training at step 504 does not require setting certainsignal strengths. In some embodiments, training may comprise trainingthe security system 400 to associate a particular transmitted signal(e.g., having a particular frequency, transmitting particular data,etc.) with the vehicle security node 440 so that integration of thesecurity system 400 with the vehicle security node 440 may beauthorized.

When the user has finished defining the acceptable range(s) of signalstrength, the process may proceed to step 505. At step 505, the user candefine any additional desired parameters. For example, if the user wantsdifferent behavior for different days of the week and times of day, thenthe user can define time ranges as additional parameters. Any otherdesired parameter can be combined as well (e.g., state of televisionviewing, number of cars in the garage, season of the year, outsidetemperature, etc.).

After setting any desired additional parameters, the process may move tostep 506. At step 506, the user can define the security system's alarmreactions for the various parameters. In one or more arrangements, thesecurity system 400 may be programmed to arm itself when it isdetermined that the vehicle 301 is not within the registered position.That is, the security system 400 may instructed to enter an armed statewhen the signal strength of the signal received from the vehiclesecurity node 440 drops below a certain threshold. Further, the securitysystem 400 may be programmed to perform other intervening steps. Forexample, the security system 400 may be programmed to send a signal(e.g., a text message, email, satellite signal) to a designated userdevice (e.g., a device of the driver of the vehicle that left, such as atablet, smartphone, GPS, etc.) to request whether the security system400 should be armed. Another example intervening step may be todetermine based on a predefined schedule (e.g., a user defined schedule)whether the security system 400 should be armed. Still another exampleintervening step may be to monitor motion sensors, cameras, heatsensors, etc. to detect whether anyone is remaining in the premises 300so that the premises 300 may only be armed if the security system 400determines that no one else remains at the premises 300. It should beunderstood that a combination of these intervening steps may also beperformed.

Other reactions defined at step 506 may be to turn on lights, open agarage door, and/or disarm the security system 400 when the vehicleenters the registered position or zone. Yet another reaction may be totrigger the vehicle's pre-existing alarm system (and thereby alert anypersons in the vicinity of the vehicle) when the security system 400detects an alarm event associated with the premises 300, or to alert thesecurity system 400 to send an alert signal when the vehicle's alarmsystem is triggered. For example, if a home security system alarm istriggered because of a smoke alarm tripping, or because a burglar opensa window, the home security system can instruct a nearby automobilealarm to also begin sounding its general or specific alarm, helping toalert others to the problem. Conversely, if an automobile alarm istriggered due to a thief breaking a car window, the automobile alarmsystem can send a signal to the homeowner's home alarm system, and thehome alarm system can sound its own alarm, helping to alert others tothe problem. In light of the above, it should be evident that a numberof reactions may be defined at step 506.

After the alarm reactions have been defined, the process may then storethe registered location (e.g., signal strengths associated with theregistered location) or other information from the signal transmitted bythe vehicle security node 440, additional parameters, and reactions in aprofile on the memory 442 of vehicle security node 440, the memory 432of the gateway 430, the memory 422 of the alarm panel 420, and/or memoryof the local office 302 at step 507. The profile can become apredetermined profile for other vehicle security nodes 440 added in thefuture, and can be labeled according to the vehicle 301 it serves.

FIG. 6 illustrates an example process in accordance with an aspect ofthe present disclosure. More specifically, FIG. 6 shows steps in aprocess of reacting to movement of a vehicle 301 away from, or out ofthe proximity of, its corresponding security system 400. FIG. 6 beginswith step 601 in which the security system 400 monitors the status ofthe vehicle security node 440. In step 601, the security system 400 mayperiodically detect a signal strength of a signal emitted from thevehicle security node 440. If the security system 400 determines thatthe signal strength is greater than a predetermined signal strengththreshold, then the security system 400 determines that the vehiclesecurity node 440 is in range of the security system 400 at step 601.However, if the security system 400 determines that the signal strengthis less than or equal to the predefined signal strength threshold, thenthe security system 400 determines that the vehicle security node 440 isout of range. Herein, the predetermined signal strength threshold may beobtained from a predefined profile or set by a user or operator of thesecurity system 400, an installer of the vehicle security node 440, orany other authorized person. In some embodiments, the predeterminedsignal strength threshold may be the minimum signal strength that isneeded to communicate between the vehicle security node 440 and securitysystem 400.

If the vehicle security node 440 is in range (Yes at step 601), thesecurity system 400 may wait a predetermined period of time beforeperforming step 601 again. But, if the security system 400 is out ofrange (No at step 601), the process proceeds to step 602. In someembodiments, the security system 400 may have to determine that thevehicle security node 440 is out of range for a certain period of timeor determine that a certain number of out of range determinations havebeen made before proceeding to step 602.

In step 602, the security system 400 may be armed. The security system400 may be armed immediately or soon after the security system 400detects that the vehicle security node 440 is out of range.Alternatively, the security system 400 may enter a pre-arm mode in whichthe security system 400 detects whether certain events, such as thetriggering of a motion sensor, occur in a set period of time beforearming the security system 400. For example, when the vehicle securitynode 440 becomes out of range, the security system 400 may wait to seeif motion sensors or cameras 310 in the premises 300 are triggeredthereby indicating that someone is still in the premises 300, beforearming the security system 400. In this manner, the security system 400may prevent arming itself when not all people have left the premises300. Whether the security system 400 is armed immediately or a pre-armmode is entered may be defined by a profile. The profile may take intoconsideration programmed or learned habits or characteristics of thoseentering and exiting the premises 300. For example, the profile maylearn to arm the security system 400 immediately if the vehicle securitynode 440 moves out of range at approximately 8:00 am on a weekday when aperson leaves for work. Or, for example, the profile may be programmedto cause the security system 400 to enter a pre-arm mode when thevehicle security node 440 moves out of range because the programmerknows that multiple people reside at the premises.

Additionally, or alternatively, step 602 may include performing asecurity system check to determine the status of the security system400. For instance, the security system 400 may monitor one or more ofits sensors to detect whether a door 304 or window 305 is open orcertain lights are on. As part of the security system check, thesecurity system 400 may compare its findings against a profile todetermine if certain findings are acceptable. For example, a profile mayindicate that a particular window 305 may remain open or particularlights may remain on, and therefore, the security system check might notreport these findings.

Step 603 may be performed to notify a certain person of the results ofstep 602. That is, the security system 400 may send a notice to one ormore designated user devices indicating whether the security system 400was armed or not, whether the security system 400 entered into a pre-armmode, or what was discovered as a result of the security system check.The notice may be in the form of a text message, an email, a satellitemessage, an alert message displayed on a web portal, etc. and may besent in response to actions taken in step 602. In one aspect of thedisclosure, a notice (e.g., a text message) may be sent to the portabledevice 901 or a smartphone or tablet of a particular user associatedwith the vehicle including the vehicle security node 440 to indicatethat the security system 400 has been armed or has entered into apre-arm mode. The notice may also indicate that lights were left on orthat a door 304 or window 305 was left open so that the user may returnto the premises 300 to remedy the situation if he/she so desires. Themessage may be sent relatively soon after the vehicle 301 leaves thepremises 300, so that the return trip to the premises 300 is reduced.

In another aspect of the disclosure, the notice may be displayed on ascreen (e.g., a GPS display) or played through a speaker within thevehicle 301 that left the premises 300. This notice may be receivedthrough a wireless connection (e.g., cellular connection, satelliteconnection, etc.). Alternatively, this notice may be generated frominformation obtained by the vehicle security node 440 prior to movingout of range and losing communication with the security system 400.While the vehicle security node 440 is in range, it may communicate backand forth with the security system 400 to ascertain informationregarding the security system 400, such as whether the security system400 is armed or not, what doors/windows are open, what lights are on,etc. This information may be ascertained periodically or continuously.Therefore, the vehicle security node 440 may know the state of thesecurity system 400 at the time it loses communication with the securitysystem 400. Based on this ascertained information, the vehicle securitynode 440 may generate a notice, and deliver the notice to those in thevehicle 301 having the vehicle security node 440. In some embodiments,the vehicle security node 440 and/or security system 400 may detect thatthe vehicle security node 440 is nearly out of range based on aweakening signal strength, and in response, send the latest informationregarding the security system 400 at this time.

Further, in some embodiments, step 603 may be performed prior to step602. A notice may be sent to prompt the particular user to select howthe security system 400 should perform. For example, the notice mayprompt the user to select whether or not to arm the security system 400,whether or not to enter into a pre-arm mode, and/or whether to turnon/off lights, lock doors, turn on/off a television, adjust athermostat, etc.

FIG. 7 illustrates an example process in accordance with another aspectof the present disclosure. More specifically, FIG. 7 shows steps in aprocess of reacting to the reentry of a registered vehicle security node440 into the proximity of the security system 400. FIG. 7 begins withstep 701, which performs similar functions to those described above withregards to step 601. That is, step 701 may compare signal strength witha predetermined signal strength threshold to determine whether thevehicle security node 440 is in range of the security system 400.However, if the security system 400 determines that the vehicle securitynode 440 is not in range at step 701 (No at step 701), the securitysystem 400 may wait a predetermined period of time before performingstep 701 again. Step 701 may be repeated until the security system 400determines that the vehicle security node 440 is back in range. Once thevehicle security node 440 is determined to be in range (Yes at step701), the process proceeds to step 702.

In step 702, the security system 400 may authenticate the vehiclesecurity node 440. That is, the vehicle security node 440 may provide akey to the security system 400 to prove that it has previouslyregistered with the security system 400. Where a plurality of vehiclesecurity nodes 440 are used in the same security system 400, eachvehicle security node 440 may have its own key so that the securitysystem 400 can identify the exact vehicle security node 440 that it iscommunicating with and can respond differently to actions of differentvehicle security nodes 440. After the vehicle security node 440 isauthenticated at step 702, the process may proceed to step 703.

In step 703, the security system 400 may respond to the reentry of thepreviously registered vehicle security node 440. A profile may exist forthe particular vehicle security node 440 which may define what actionsto take in step 703. Or, the security system 400 may perform a generalresponse for all authenticated vehicle security nodes 440. One responsethat may be performed at step 703 may include the security system 400turning on lights in or outside of the premises 300. In someembodiments, the response may depend on a schedule so that, for example,outside lights are turned on if the vehicle security node 440 returns atnight. Another response that may be performed may be to open a garagedoor or gate. Or, if the particular security system 400 is not capableof controlling the operation of the garage door or gate, it may at leastdisarm a portion of the security system 400 so that the alarm is nottriggered when the garage door or gate is opened.

Still another response may be to disarm the security system 400entirely. In some instances, disarming a security system 400 may bedesired only if the vehicle security node 440 is in a particularlocation. Therefore, the security system 400 may be trained to determinea vehicle security node's location from signal strength as explainedabove with reference to FIG. 5. Once trained, the security system 400may be programmed to disarm the security system only if the vehicle isin a certain location, such as in a garage. Where disarming the entiresecurity system 400 is a sensitive issue, tighter schedulingrestrictions may be implemented. In other words, a profile may requirethat it be a certain period of the day in order to disarm the securitysystem 400 in response to detecting the reentry of the vehicle securitynode 440. As a result of entirely disarming the security system 400, aperson may not have to enter a security code on a keypad of the alarmpanel 420 when he/she enters the premises 300.

Additionally, or alternatively, the response of step 703 may be toimplement the vehicle alarm system (i.e., the pre-existing vehicle alarmsystem and/or vehicles sensors 311) into the security system 400. Thismay entail a bi-directional exchange of information between the vehiclesecurity node 440 and the security system 400. As a result, an alarmevent detected by the vehicle's alarm system may be transmitted from thevehicle security node 440 to the security system 400 to trigger thesecurity system 400 to react (e.g., make noise, turn on lights, recordvideo, call authorities, etc.). Vice versa, an alarm event detected bythe security system 400 may be transmitted to the vehicle's alarm systemto trigger a reaction (e.g., horn sounds, flashing lights, etc.). Thus,the vehicle alarm system may become an extension of the security system400 and the security system 400 may become an extension of the vehiclealarm system.

FIG. 8 illustrates an example process in accordance with yet anotheraspect of the present disclosure. More specifically, FIG. 8 shows stepsin a process of communicating with a vehicle security node 440 throughan interface of the security system 400. The process of FIG. 8 beginswith step 801 in which a user input is received by the security system400. The user input may be received through any interface of thesecurity system 400, such as the alarm panel 420 (or the portable device901), the television 303, a device (e.g., smartphone) having a securitysystem application stored thereon, a computer within the premises 300,and the web portal. Further, the user input may be a request forinformation from the vehicle security node 440 or a command. The requestfor information may include a request for vehicle diagnostic information(e.g., engine status, fuel status, battery status, tire pressure, oiltemperature, and other information ascertained through the OBD-IIconnector). Additionally, or alternatively, the requested informationmay include vehicle alarm information (e.g., whether the doors arelocked, windows are closed, whether the vehicle alarm is on, etc.).Meanwhile, examples of commands that may be sent include commands toturn on a vehicle alarm, lock doors, close windows, begin/end charging abattery, turn on heat or air conditioning, start an engine, etc. Wheremultiple vehicle security nodes 440 are registered with the samesecurity system 400, the user input may specify the particular vehicle301 that the command or request is directed to.

At step 802, data in accordance with the received user input istransmitted to the vehicle security node 440. The security system 400may first interpret the user input and generate data to instruct thevehicle security node 440 to perform a command or provide informationbefore transmitting the data. The transmission may occur via a wiredconnection or a wireless connection. Any protocol may be used totransmit the data to the vehicle security node 440. In some embodiments,step 802 may include detecting a signal strength of the vehicle securitynode 440 to determine whether the data may be transmitted. If thedetected signal strength is below a predetermined threshold, then thesecurity system 400 may alert the user that the data could not be sent.

Once the data is received at the vehicle security node 440, step 803 isperformed. In step 803, the vehicle security node 440 interprets thedata received from the security system 400. If the data is related to acommand, then the vehicle security node 440 instructs the appropriatedevices to perform the command. For example, if the data pertains to acommand to lock the doors, the vehicle security node 440 may command thedoor locks to move to the lock position. Meanwhile, if the data isrelated to a request, then the vehicle security node 440 retrievesinformation to fulfill the request. For example, if the data pertains toa request for diagnostic information, the vehicle security node 440 mayscan the vehicle's bus using, for example, the OBD-II connector, andascertain the appropriate codes.

Next, in step 804, the vehicle security node 440 may generate a reportto transmit back to the security system 400. The report may include theinformation the user requested or may include a confirmation indicatingwhether or not the command the user inputted was performed. Where theinformation requested is diagnostic information, the vehicle securitynode 440 may translate the codes into more descriptive messages, andsend back the descriptive messages. In other embodiments, the vehiclesecurity node 440 may instead transmit the codes, and the codes may betranslated by the security system 400. To perform the translation, thesecurity system 400 may request the translation through the gateway 430.Thus, changes in code meanings may be made upstream thereby avoidingpossible inconvenience to a user.

Although FIG. 8 shows that steps 803 and 804 are performed in responseto a user input at step 801, this is not necessary. In some embodiments,step 803 and/or step 804 may be performed in response to scheduledsettings or people actions. That is, the security system 400 mayautomatically instruct the vehicle security node to perform certaincommands or provide certain information according to a schedule orpeople actions. For example, when all lights are turned off at night,the security system 400 may send a command to the vehicle security node440 to lock its doors and/or arm its vehicle alarm system. Or, forexample, when a user arms the security system 400 at night, the vehiclesecurity node 440 may automatically report information about the vehicle301, such as whether the vehicle 301 doors are locked, whether thevehicle 301 windows are open, whether the vehicle 301 battery is dead,etc. In another example, the vehicle security node 440 may automaticallyarm the vehicle 301 if it is in range at 10:00 pm according to a setschedule.

The features described above are examples of various concepts, and theymay be modified in any desired manner. For example, various elements andsteps may be divided, combined, rearranged, omitted, and augmented asdesired. The various elements may be implemented using computercomponents, such as processors and computer-readable memories, and anyof the elements described herein may be implemented using software,hardware (e.g., similar to that shown in FIG. 2), or any combination ofthe two. The scope of this patent should only be limited by the claimsthat follow.

1. A method, comprising: receiving, by a premises security system, asignal transmitted from a mobile security node on a mobile device via aconnection that comprises a wireless link; authenticating the mobilesecurity node; and integrating an alarm of the mobile device with thepremises security system.
 2. The method of claim 1, further comprising:transmitting data from the premises security system to the mobilesecurity node.
 3. The method of claim 2, further comprising: receiving,by the premises security system, a report from the mobile security nodein response to the transmitting of the data, wherein the data is one ofa request for information regarding the mobile device and a commandinstructing the mobile device to perform a function.
 4. The method ofclaim 3, wherein the report includes the information requested when thedata is a request for information, and wherein the report includes aconfirmation that the function has been performed when the data is acommand.
 5. The method of claim 4, wherein the mobile device comprises avehicle, and wherein the request for information includes one of arequest for vehicle diagnostic information and vehicle alarminformation.
 6. The method of claim 4, wherein the mobile devicecomprises a vehicle, and wherein the command includes one of a commandto turn on the vehicle's alarm, lock the vehicle's doors, close thevehicle's windows, begin charging the vehicle's battery, finish chargingthe vehicle's battery, control the vehicle's internal temperature, andstart the vehicle's engine.
 7. The method of claim 1, furthercomprising: determining whether the mobile security node is in rangebased on a signal strength of the signal received from the mobilesecurity node.
 8. The method of claim 7, wherein the range is definedaccording to a predefined profile acquired with the mobile securitynode.
 9. The method of claim 7, further comprising: defining the rangeby training the premises security system to determine that the mobilesecurity node is in range when the signal strength of the receivedsignal is approximately a certain signal strength.
 10. The method ofclaim 1, further comprising: determining, by a home security computingdevice, that a homeowner's car is parked in the home's driveway orgarage; detecting an alarm signal from a car alarm system of thehomeowner's car; and in response to the car alarm signal, triggering ahome alarm signal.
 11. The method of claim 1, further comprising:determining whether the mobile security node is out of range based on asignal strength of the signal received from the mobile security node;and in response to determining that the mobile security node is out ofrange, performing one of arming the premises security system, promptinga user to determine whether to arm the premises security system, andinstructing the premises security system to monitor a premises for apredetermined period of time.
 12. The method of claim 1, wherein thealarm of the mobile device is triggered if at least one sensor of thepremises security system is triggered.
 13. The method of claim 1,wherein an alarm of the premises security system is triggered if thealarm of the mobile device integrated with the premises security systemis triggered.
 14. A method comprising: receiving a signal transmittedfrom a mobile security node on a mobile device via a connection thatcomprises a wireless link; determining whether the mobile security nodeis out of range based on a signal strength of the signal received fromthe mobile security node; and in response to determining that the mobilesecurity node is out of range, performing one of arming a premisessecurity system, prompting a user to determine whether to arm thepremises security system, and instructing the premises security systemto monitor a premises for a predetermined period of time.
 15. The methodof claim 14, further comprising: integrating an alarm of the mobiledevice with the premises security system in response to receiving thesignal transmitted from the mobile security node.
 16. The method ofclaim 14, further comprising: transmitting data from the premisessecurity system to the mobile security node; and receiving, by thepremises security system, a report from the mobile security node inresponse to the transmitting of the data, wherein the data is one of arequest for information regarding the mobile device and a commandinstructing the mobile device to perform a function.
 17. The method ofclaim 14, further comprising: determining whether the mobile securitynode is in range based on a signal strength of the signal received fromthe mobile security node.
 18. The method of claim 17, furthercomprising: defining the range by training a premises security system todetermine that the mobile security node is in range when the signalstrength of the received signal is approximately a certain signalstrength.
 19. The method of claim 14, further comprising: triggering analarm of the mobile device if at least one sensor of the premisessecurity system is triggered; and triggering an alarm of the premisessecurity system if the alarm of the mobile device is triggered.
 20. Amethod comprising: receiving a signal transmitted from a mobile securitynode on a mobile device via a connection that comprises a wireless link;determining whether the mobile security node includes an authenticatedmobile security node based on the received signal; and in response todetermining that the mobile security node includes an authenticatedmobile security node, performing one of disarming a premises securitysystem that monitors a premises, opening a door on the premises,unlocking a door on the premises, and turning on a light on thepremises.